Skip Headers

Oracle® Database Backup and Recovery Reference 10g Release 2 (10.2) Part Number B14194-03 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# STARTUP

Syntax

startup::=

Description of the illustration startup.gif

Purpose

To start the target database from within the RMAN environment. This command is equivalent to using the SQL*Plus `STARTUP` command. You can:

- Start the instance without mounting a database.

- Start the instance and mount the database, but leave it closed.

- Start the instance, and mount and open the database in:

  - unrestricted mode (accessible to all users)

  - restricted mode (accessible to DBAs only)

Additionally, the RMAN `STARTUP` command can start an instance in `NOMOUNT` mode even if no server parameter file or initialization parameter file exists. This feature is useful when you need to restore a lost server parameter file.

See Also: Oracle Database Administrator's Guide to learn how to start up and shut down a database, and SQL*Plus User's Guide and Reference for SQL*Plus `STARTUP` syntax

Restrictions and Usage Notes

- You cannot use the RMAN `STARTUP` command to open the recovery catalog database: execute a `STARTUP` statement in a SQL*Plus session instead.

Keywords and Parameters

If you do not specify any options, then RMAN mounts and opens the database with the default server parameter file.

Syntax Element | Description
--- | ---
`STARTUP` | If you specify only `STARTUP` with no other options, then the instance starts, then mounts and open the database.
`DBA` | Restricts access to users with the `RESTRICTED` `SESSION` privilege.
`FORCE` | If the database is open, then `FORCE` shuts down the database with a SHUTDOWN `ABORT` statement before re-opening it.If the database is closed, then `FORCE` opens the database.
`MOUNT` | Starts the instance, then mounts the database without opening it
`NOMOUNT` | Starts the instance without mounting the database. If no parameter file exists, then RMAN starts the instance with a "dummy" parameter file. You can then run `RESTORE` `SPFILE` to restore a backup server parameter file.
`PFILE` `=` `'filename'` | Specifies the filename of the `init.ora` file for the target database. If this parameter is not specified, then the default `init.ora` filename is used.

Examples

Opening the Database by Using the Default Parameter File: Example This example starts and opens the database:

    STARTUP;

Mounting the Database While Specifying the Parameter File: Example This example forces a `SHUTDOWN` `ABORT` and then mounts the database with restricted access, specifying a nondefault parameter file location:

    STARTUP FORCE MOUNT DBA PFILE=/tmp/initTRGT.ora;

Starting an Instance Without a Parameter File: Example The following example starts an instance without using a parameter file, then runs `RESTORE` `SPFILE`:

    SET DBID 1447326980;
    STARTUP FORCE NOMOUNT; # RMAN starts instance with dummy parameter file
    RESTORE SPFILE FROM AUTOBACKUP; # restore a server parameter file
    STARTUP FORCE; # restart instance with restored server parameter file